Comments
-
FInally, there was an issue of routing from the SD-WAN to the SonicWall, host provider fix it and now, it's OK, we can join the remote server from the LAN 192.168.0.x over the SD-WAN connection.
-
Yes the SonicWall can ping the VeloCloud and the traffic going out via the X2
-
Thanks ArkWright for this precisions. I confirm to you we aren't translating the destination. In the meantime, I have already change the Translated Destination to "Original" but no effects. I set the metric of 10 because all others routing policies have a metric of 20 but I have change to 1 on your advice.
-
I have tried to change the Source Subnet with X0 for the NAT but it's seems that's not running.
-
Indeed, the client accesses a remote server via an IPSec VPN but apparently, the latter is not stable enough, which is why the host provided an SD-WAN box which must be connected to the Internet therefore via the router Customer Internet. The host provider requests that the network flow that arrives to it be addressed in…
-
Thank you verry much TKWITS, I have allow "Use Routed Mode - Add NAT Policy to prevent outbound\inbound translation checkbox to enable Routed Mode for the interface X0" on each SonicWall. Next, I have add the static route below: Site A Source: 192.168.0.0 /24 Destination: 172.16.0.0 /24 Service: Any Gateway: X1 Default…
-
I have solve the issue like this: Site A : SonicWall TZ 400 WAN : 1.2.3.4 LAN : 192.168.0.x Server : 192.168.0.253 - https port from the LAN Note: From the WAN, Server accessible on port number 4000 (NAT from port 4000 to https) ---------------------------- Site B : SonicWall TZ 300 WAN : 4.3.2.1 LAN 192.168.1.x About…
-
On Site A I have this log entry: Message: TCP connection reject received ; TCP connection dropped Source: 192.168.0.253, 4000, X0 Destination: 192.168.1.58, 13490, X1 IP Protocol: tcp Notes: TCP Flag(s): ACK RST
-
I understand. So, I have created this NAT rule on Site B as you mentioned above: Source Original: LAN Subnets (192.168.1.0/24) Source Translated: Original Destination Original: SRV-APP Public IP (=Address Objetc >> Host 1.2.3.4 - Zone: VPN) Destination Translated: SRV-APP Private IP (=Address Objetc >> Host 192.168.0.253 -…
-
I just solve the issue: I have add network port TCP 4000 in ACL LAN to WAN on the "Site B" and now it's OK, I can access from the "Site B" through the VPN Site to Site to the Server on the "Site A" with his WAN address https://1.2.3.4:4000
-
Hi, I have try your solution (NAT + ACL) but the result is the same unfortunately...
-
The situation is I need to access a Server on "Site A" by using the WAN IP of the Site A from a "Site B" through the VPN Site to Site (between "Site A" and "Site B"). From the WAN (Internet), I can access the Server on "Site A" without problem via its Public IP (NAT WAN to LAN) ; It also works from "Site A" LAN, still…